…n CI

- Pin net.minestom:minestom to 2026.05.17-1.21.11 (current Maven Central
  release) instead of the BOM-resolved version so the deployable jar runs
  on the latest Minestom regardless of aonyx/mycelium BOM lag.
- Bump butterfly 1.0.21 -> 1.0.23 to match the current Butterfly release.
- Harden the application shadowJar: strip jar signatures and module-info
  and exclude duplicates so the relocation-free fat jar built from the
  shaded LuckPerms fork stays loadable.
- Pin the reusable PR/publish workflows to the v2.1.0 release tag instead
  of a temporary branch ref.

https://claude.ai/code/session_01S76fk9ma5Szkf9r1W44RVP

Titan shaded net.luckperms common/minestom/minestom-app/loader-utils
into the relocation-free fat jar and bootstrapped LPMinestomBootstrap
directly on the app classpath, defeating LuckPerms' dependency
isolation. Switch to the LuckPerms-designed loader:

- depend on net.luckperms:minestom-loader (runtimeOnly, not shaded)
- net.luckperms:api becomes a runtime (implementation) dependency so
  LuckPermsProvider resolves on the host classpath while the JarInJar
  child loads the isolated implementation against the same API classes
- drop Titan's custom MinestomLoader; TitanApplication now uses the
  fork's me.lucko.luckperms.minestom.loader.MinestomLoader
- add the minestom-loader version catalog entry
- generalise the shadowJar signature/module-info hardening comment

https://claude.ai/code/session_01S76fk9ma5Szkf9r1W44RVP

TitanApplication references me.lucko.luckperms.minestom.loader.MinestomLoader
directly, so the loader is needed at compile time; runtimeOnly removed it
from compileClasspath and broke compilation. Use implementation: the
minestom-loader artifact is a thin JarInJar wrapper with no heavy
transitive dependencies (adventure/configurate live inside the embedded
luckperms-minestom.jarinjar resource), so this does not reintroduce raw
shading of common/minestom.

https://claude.ai/code/session_01S76fk9ma5Szkf9r1W44RVP

Pinning Minestom to 2026.05.17-1.21.11 decoupled it from the OLF BOM
that also governs the cyano test harness; cyano 0.7.1 was built against
an older Minestom, so RegistryData's static initializer threw
NoSuchMethodError and all Minestom-backed tests failed. aonyx-bom 0.7.2
aligns cyano with Minestom 2026.05.17-1.21.11.

https://claude.ai/code/session_01S76fk9ma5Szkf9r1W44RVP

enforcedPlatform(mycelium-bom) pinned net.kyori:adventure-* classpath-
wide; the pinned Adventure was older than Minestom 2026.05.17-1.21.11
requires, so MinestomFlattenerProvider.<clinit> failed with
NoSuchMethodError: ComponentFlattener.toBuilder(). Switching to
platform(...) keeps the BOM as a version recommendation that Gradle can
upgrade to satisfy Minestom's transitive Adventure version requirement.
Applied in :common and :setup, the two modules using enforcedPlatform.

https://claude.ai/code/session_01S76fk9ma5Szkf9r1W44RVP

aonyx-bom 0.7.2 was never published (latest release is 0.7.3); bump to
the existing version. Also align mycelium-bom to 1.6.5, let minestom be
managed by the BOM, bump aves to 1.14.0, and trim the unused LuckPerms
catalog entries down to the minestom-loader.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

aves 1.14.1 reworked BaseMap into an immutable type: accessors are now
name()/spawn()/builders() (List<String>) instead of getName()/getSpawn()/
getBuilders(), there are no setters, and the only constructor is
BaseMap(String, Pos, List<String>).

Give LobbyMap a matching constructor, build instances through it in
LobbyMapBuilder (dropping the dead setter calls), and update MapProvider,
the app/setup listeners and the tests to the new accessors.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>